Communicating property data

ABSTRACT

A system for communicating property data includes one or more interfaces operable to receive lien data including an identification of a lien on a property, an identification of the holder of the lien, a balance of debt associated with the lien, and a repayment schedule for the amount of debt associated with the lien; and lien authentication data including one or more from the set comprising: a copy of an agreement memorializing the lien, a property title memorializing the lien, and a government record memorializing the lien; one or more memories operable to store the received lien data and the received lien authentication data; and one or more processors operable to: determine, based on the received lien authentication data, that the received lien data is valid, and determine, based on the received lien data, that the received balance of debt associated with the lien needs to be updated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/847,515 filed Sep. 8, 2015, by Joseph B. Castinado et al., andentitled “COMMUNICATING PROPERTY DATA,” which is incorporated herein byreference.

TECHNICAL FIELD

This disclosure relates generally to communicating property data, andmore particularly to communicating property data related to obligationsattached to the property.

BACKGROUND

Property, such as real-estate and vehicles, is often encumbered byliens. It is non-trivial and time consuming to determine whether aparticular property has encumbrances, such as liens. The difficulty indetermining whether a property is encumbered by liens is especiallyproblematic when dealing with conveying the property and with insurancepayments on property. For example, a property owner may demand rapidpayment from an insurance company of an insurance claim on a property,however, if the property is encumbered by one or more liens, otherparties (e.g., lien holders) may be entitled to a portion of theinsurance payment.

SUMMARY OF EXAMPLE EMBODIMENTS

According to embodiments of the present disclosure, disadvantages andproblems associated with providing internal services to externalenterprises may be reduced or eliminated.

In certain embodiments, a system for communicating property dataincludes one or more interfaces operable to receive lien data, the liendata including an identification of a lien on a property, anidentification of the holder of the lien, a balance of debt associatedwith the lien, and a repayment schedule for the amount of debtassociated with the lien; and lien authentication data, the lienauthentication data including one or more from the set comprising: acopy of an agreement memorializing the lien, a property titlememorializing the lien, and a government record memorializing the lien;one or more memories communicatively coupled to the one or moreinterfaces, the one or more memories operable to store the received liendata and the received lien authentication data; and one or moreprocessors communicatively coupled to the one or more memories, the oneor more processors operable to: determine, based on the received lienauthentication data, that the received lien data is valid, anddetermine, based on the received lien data, that the received balance ofdebt associated with the lien needs to be updated.

In particular embodiments, a system for communicating property data,comprising one or more memories operable to store a lien data for aplurality of properties, the lien data including: an identification of alien on a property, an identification of the holder of the lien, and abalance of debt associated with the lien; and one or more interfacescommunicatively coupled to the one or more memories, the one or moreinterfaces operable to receive a property payment request from arequesting party, the property payment request including anidentification of a subject property; and one or more processorscommunicatively coupled to the one or more memories, the one or moreprocessors operable to: determine that the subject property is one ofthe plurality of properties stored on the one or more memories,determine one or more liens associated with the subject property, anddetermine the lien holder for each determined lien associated with thesubject party.

Certain embodiments of the present disclosure may provide one or moretechnical advantages having specific technical effects.

In certain embodiments, a system is operable to provide a centralizedrepository associating property with liens, thereby conserving thecomputational resources and bandwidth consumed by searching disparateresources to identify liens on a property.

In particular embodiments, a system is operable to determine an amountof debt associated with one or more liens on a property, therebyconserving the computational resources and bandwidth consumed bysearching disparate resources to determine an amount of debt associatedwith a property.

In an embodiment, a system is operable to allocate a payment associatedwith a property between the property owner and lien holders, therebyconserving the computational resources and bandwidth consumed bysearching disparate resources to determine payment allocations for theproperty owner and lien holders.

Other technical advantages of the present disclosure will be readilyapparent to one skilled in the art from the following figures,descriptions, and claims. Moreover, while specific advantages have beenenumerated above, various embodiments may include all, some, or none ofthe enumerated advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and forfurther features and advantages thereof, reference is now made to thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates an example system for communicating property data;

FIG. 2 illustrates a table from a database of an example system forcommunicating property data;

FIG. 3 illustrates a flow diagram of an example method for communicatingproperty data, according to certain embodiments of the presentdisclosure; and

FIG. 4 illustrates a flow diagram of an example method for communicatingproperty data, according to certain embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure and its advantages are bestunderstood by referring to FIGS. 1 through 4 of the drawings, likenumerals being used for like and corresponding parts of the variousdrawings.

In an example, a system includes a lien holder interface module operableto receive lien data from lien holders and store the lien data in acentralized database. The lien holder interface module may be operableto determine liens associated with properties, debt balances associatedwith liens, and to interface with interested entities to disbursepayments associated with property encumbered by liens to the lienholders and to the property owner.

FIG. 1 illustrates an example system 100 for communicating propertydata. According to an embodiment, system 100 includes property owners110, member financial institutions 120, third party lien holders 130,and lien holder interface module 140, interested entities 150, andnetwork 160.

Property owners 110 represent entities that own property, for example,real-estate, vehicles, or any other type of property. Property owners110 may be individuals, companies, or other entity that owns property.In an embodiment, property owners 110 may have an encumbered interest ina property. For example, a property may be encumbered with liens on theproperty, which represent a non-possessory security interest in theproperty. Liens may be memorialized in property ownership documents(e.g., a title), agreements between property owners 110 and lienholders, in government records (e.g., publically registered documents),or in any other suitable form. In certain embodiments, liens areassociated with an amount of debt secured by property of property owners110, and the debt may have a particular repayment schedule (e.g., anamortization schedule).

Member financial institutions 120 represent a plurality of financialinstitutions 132 that have entered into an agreement (e.g., a jointventure, contractual agreement, and/or other suitable agreement) tomaintain a centralized repository (e.g., database 128 of lien holderinterface module 140) of property information, such as identification ofliens on property. Financial institutions 120 may include organizationssuch as commercial banks, savings and loan associations, credit unions,Internet banks, mutual fund companies, brokerage firms, credit cardcompanies, or other entity. In certain embodiments, financialinstitutions 120 have different business units or subdivisions thathandle different business activities.

Member financial institutions 120 may have liens on a number ofproperties (e.g., vehicles, real-estate, or other property) andcommunicate lien data to lien holder interface module 140. Lien data mayinclude an identification of a lien on a property, an identification ofthe holder of the lien (e.g., the lien holder), an identification of theproperty subject to the lien (e.g., an address, a vehicle identificationnumber (“VIN”), or other suitable property identifier), anidentification of the type of property subject to the lien (e.g., car,boat, recreational vehicle, motorcycle, first home, second home,business, or other suitable property categorization), a balance of debtassociated with the lien, a debt repayment schedule associated with thelien, an identification of the property owner (e.g., property owner110), or any other suitable information associated with a lien or aproperty. Member financial institutions 120 may further communicate lienauthentication data to lien holder interface module 140. Lienauthentication data represents information that can be used (e.g., bylien holder interface module 140) to validate a lien, such as anagreement between the lien holder and the property owner memorizing thelien, a property title memorializing the lien, a government recordmemorializing the lien, or any other suitable information operable tovalidate a lien on a property.

Third party lien holders 130 represent lien holders that are not memberfinancial institutions 120, but that hold liens on property. Third partylien holders 130 may include organizations such as commercial banks,savings and loan associations, credit unions, Internet banks, mutualfund companies, brokerage firms, credit card companies, vehicledealerships, vehicle manufacturers, contractors, developers, or anyother type of lien holder. In certain embodiments, third party lienholders 130 may submit lien data to lien holder interface module 140.For example, member financial institutions 120 may charge a fee formaintaining third party lien holder 130 lien data (e.g., in database 128of lien holder interface module). The fee may be based on the type ofproperty associated with the lien, the amount of debt associated withthe lien, the particular third party lien holder 130, or any othersuitable information. In certain embodiments, lien holder interfacemodule 140 is operable to communicate fee requests, for example, tothird party lien holders 130 or member financial institutions 120, andto receive payments on the communicated fee requests for example, tothird party lien holders 130 or member financial institutions 120.

Lien holder interface module 140 represents a component of system 100operable to maintain lien data received from one or more of memberfinancial institutions 120 and third party lien holders 130. Lien holderinterface module 140 may further be operable to receive requests forlien data from member financial institutions 120, third party lienholders 130, or interested entities 150. In certain embodiments, lienholder interface module 140 is operable to interface with one or more ofproperty owners 110, member financial institutions 120, third party lienholders 130, and interested entities 150. Lien holder interface module140 may include one or more processors 142, interfaces 144, memories146, and databases 148.

In an embodiment, lien holder interface module 140 is operable toreceive lien data and/or lien authentication data, for example, frommember financial institutions 120 and/or third party lien holders 130.In certain embodiments, member financial institutions 120 have arelationship (e.g., a joint venture, contractual agreement, and/or othersuitable agreement) such that lien data from each of the memberfinancial institutions 120 is trusted. For example, member financialinstitutions 120 may not be required to submit lien authentication datato lien holder interface module 140, while third party lien holders 130may be required to submit lien authentication data. Alternatively,member financial institutions 120 may be required to submit differentlien authentication data to lien holder interface module 140 than thirdparty lien holders 130. In particular embodiments, lien holder interfacemodule 140 is operable validate lien data, for example, based on lienauthentication data. Lien holder interface module 140 may comparereceived lien data to received lien authentication data to determinewhether the lien data matches the lien authentication data to validatethat the lien data is accurate. Lien holder interface module 140 maystore received lien data and/or lien authentication data in database148.

In certain embodiments, lien holder interface module 140 is operable tosearch database 148 and determine whether a property is listed indatabase 148, and if the property is listed to identify liens and liendata associated with the property. Lien holder interface module 140 maybe operable to determine whether stored lien data is current or whetherstored lien data needs to be updated. For example, a lien may beassociated with a debt balance and a debt repayment schedule and lienholder interface module 140 may be operable to determine whether thedebt balance needs to be updated based on the debt repayment schedule.If the lien balance has not been updated by the lien holder for a timeperiod (e.g., for a time period longer than the payment periodsdescribed by the debt repayment schedule), lien holder interface module140 may determine that the debt balance needs to be updated and send amessage to the lien holder requesting an update to the lien data. In anembodiment, if lien data is not updated, lien holder interface modulemay designate it as unreliable and may not consider the lien data inoperations (e.g., payment disbursements, lien searches, etc.) performedby lien holder interface module 140.

Lien holder interface module 140 may be operable to receive a propertypayment request (e.g., from interested entities 150), for example, apayment on an insurance claim associated with a property. In certainembodiments, lien holder interface module 140 searches database 148 fora property identified in a received payment request to determine whetherthere are associated liens. If lien holder interface module 140determines that there are identified liens, it may determine lienbalances associated with the identified liens. In an embodiment, lienholder interface module 140 may determine a total debt balanceassociated with a property based on the determined liens and lienbalances associated with the property. Lien holder interface module 140may be operable to determine whether a payment amount identified by thereceived payment request is greater than the determined total debtbalance associated with the property, and may be operable to communicatethe result to the interested entity 150 communicating the paymentrequest.

In particular embodiments, lien holder interface module 140 is operableto receive payment related to a property (e.g., from interested entities150) and disburse the payment to lien holders associated with theproperty and to the property owner associated with the property. Forexample, interested entity 150 may be an insurance company paying aninsurance claim for a home that was destroyed in a fire. Lien holderinterface module 140 may be operable to identify the property owner andlien holders associated with the property, determine a debt balanceassociated with each lien, and to disburse payment to the lien holdersfor the debt balance corresponding to each lien, and to disburse theremainder to the property owner. Accordingly, lien holder interfacemodule 140 can function as a clearinghouse for payments related toproperty encumbered by liens. Further, lien holder interface module 140can provide lien holders (e.g., member financial institutions 120 and/orthird party lien holders) with a centralized repository of lien data forinterested parties 150 to easily access.

Interested entities 150 represent entities that have an interest in aproperty and may include insurers of the property, prospective buyers ofthe property, prospective lenders seeking the property as security on aloan, or any other suitable entity. In an example, insurance customersmay demand rapid payment on an insurance claim in the event of damageto, or total loss of, a property. Insurance companies may compete byensuring that customers receive rapid payment in the event of a coveredinsurance claim, however, properties may be encumbered by liens wherethe lien holders have an interest in an insurance payment related toproperty. It may be less burdensome for lien holders (e.g., memberfinancial institutions 120 and third party lien holders 130) to be paiddirectly from property insurers than trying to recoup payment from theproperty owner. For example, if a vehicle was destroyed in an accidentand the vehicle owner received an insurance payment for the value of thevehicle, but still had debt to a lien holder on the vehicle, the lienholder is unsecured and must try to recoup the debt directly from theproperty owner.

Network 160 represents any suitable network operable to facilitatecommunication between components of system 100, such as property owners110, member financial institutions 120, third party lien holders 130,and lien holder interface module 140. Network 160 may include anyinterconnecting system capable of transmitting audio, video, electricalsignals, optical signals, data, messages, or any combination of thepreceding. Network 160 may include all or a portion of a public switchedtelephone network (PSTN), a public or private data network, a local areanetwork (LAN), a metropolitan area network (MAN), a wide area network(WAN), a local, regional, or global communication or computer network,such as the Internet, a wireline or wireless network, an enterpriseintranet, or any other suitable communication link, includingcombinations thereof, operable to facilitate communication between thecomponents of system 100.

A module (e.g., module 140) may execute any suitable operating systemsuch as IBM's zSeries/Operating System (z/OS), MS-DOS, PC-DOS, MAC-OS,WINDOWS, a .NET environment, UNIX, OpenVMS, or any other appropriateoperating system, including future operating systems. The functions of amodule may be performed by any suitable combination of one or moreservers or other components at one or more locations. In embodimentswhere modules represent a server, the server may be a private server,and the server may be a virtual or physical server. Additionally, amodule may include any suitable component that functions as a server.

Components of system 100, such as real-time processing module 140, mayinclude one or more processors. A processor represents any computingdevice, such as processors 142, configured to control the operation ofone or more components of system 100. A processor may comprise one ormore processors and may be a programmable logic device, amicrocontroller, a microprocessor, any suitable processing device, orany suitable combination of the preceding. A processor includes anyhardware or software that operates to control and process informationreceived by a component of system 100. In certain embodiments, aprocessor communicatively couples to other components of system 100,such as a module (e.g., module 140), an interface (e.g., interface 144),a memory (e.g., memory 146), a database (e.g., database 148), or anyother suitable component.

An interface represents any device, such as interface 144 operable toreceive input, send output, process the input or output, or performother suitable operations for a component of system 100. An interfaceincludes any port or connection, real or virtual, including any suitablehardware or software, including protocol conversion and data processingcapabilities, to communicate through network 160. In certainembodiments, an interface includes a user interface (e.g., physicalinput, graphical user interface, touchscreen, buttons, switches,transducer, or any other suitable method to receive input from a user).

A memory represents any device, such as memory 146, operable to store,either permanently or temporarily, data, operational software, or otherinformation for a processor. Memory includes any one or a combination ofvolatile or non-volatile local or remote devices suitable for storinginformation. For example, a memory may include random access memory(RAM), read only memory (ROM), magnetic storage devices, optical storagedevices, semiconductor storage devices, or any other suitableinformation storage device or a combination of these devices. A memorymay include any suitable information for use in the operation ofcomponent of system 100. A memory may further include some or all of oneor more databases (e.g., database 148).

Logic may perform the operation of any component of system 100, forexample, logic executes instructions to generate output from input.Logic may include hardware, software, or other logic. Logic may beencoded in one or more non-transitory, tangible media, such as acomputer-readable medium or any other suitable tangible medium, and mayperform operations when executed by a computer or processor. Certainlogic, such as a processor, may manage the operation of a component.

Modifications, additions, or omissions may be made to system 100. System100 may include more, fewer, or other components. Any suitable componentof system 100 may include a processor, interface, logic, memory, orother suitable element.

FIG. 2 illustrates a table 200 from a database of an example system forcommunicating property data. Table 200 includes property owner ID column202, lien ID column 204, lien type column 206, property ID column 208,lien holder ID column 210, lien balance column 212, update needed column214, property owner account ID column 216, and rows 218, 220, and 222.Columns 202-216 may include identifiers. Identifiers represent anysuitable indicia operable to identify data and may be operable touniquely identify data. For example, mailing addresses and vehicleidentification numbers (“VINs”) may be operable to uniquely identifyproperty and social security numbers may be operable to uniquelyidentify individuals.

Property owner ID column 202, represents an identifier of a propertyowner associated with a property identified in column 208. Lien IDcolumn 204 represents an identifier of a lien with a property identifiedin column 208. Lien type column 206 represents a category of lien (e.g.,car, boat, recreational vehicle, motorcycle, first home, second home,business, or other suitable property categorization). Property ID column208 represents an identifier of a property (e.g., an address or VIN).Lien holder ID column 210 represents an identifier of a lien holder(e.g., member financial institution 120 or third party lien holder 130).Lien balance column 212 represents a debt balance associated with a lienidentified in lien ID column 204. Update needed column 214 represents anindication of whether the lien data (e.g., the lien balance) needs to beupdated (e.g., the lien balance has not been updated for longer than apayment period associated with a debt repayment schedule associated withthe lien). Property owner account ID column 216 represents identifier(s)of account(s) held by member financial institutions 120 associated withthe property owner identified in column 202.

Row 218 includes “ABC123” in property owner ID column 202, “LIEN123” inlien ID column 204, “mort.” in lien type column 206, “123 4th St. City,State ZIP” in property ID column 208, “F1987” in lien holder ID column210, “$123,456” in lien balance column 212, “no” in update needed column214, and “A123, B456, C789” in property owner account ID column 216. Row218 indicates that a property owner identified as ABC123 has a mortgagelien identified as LIEN123 on a property identified by 123 4th St. City,State ZIP with a lien holder identified by F1987 that has a debt balanceof $123,456.00 and that the debt balance information has been updated.Further, the property owner identified as ABC123 has accounts withmember financial institutions 120 identified by A123, B456, and C789.

Row 220 includes “ABC123” in property owner ID column 202, “LIEN456” inlien ID column 204, “mort.” in lien type column 206, “123 4th St. City,State ZIP” in property ID column 208, “F1654” in lien holder ID column210, “$7,890” in lien balance column 212, “yes” in update needed column214, and “A123, B456, C789” in property owner account ID column 216. Row220 indicates that a property owner identified as ABC123 has a mortgagelien identified as LIEN456 on a property identified by 123 4th St. City,State ZIP with a lien holder identified by F1654 that has a debt balanceof $7,890.00 and that the debt balance information needs to be updated.Further, the property owner identified as ABC123 has accounts withmember financial institutions 120 identified by A123, B456, and C789.

Row 222 includes “DEF456” in property owner ID column 202, “LIEN789” inlien ID column 204, “vehicle” in lien type column 206, “VIN12345678” inproperty ID column 208, “FI987” in lien holder ID column 210, “$1,234”in lien balance column 212, “no” in update needed column 214, and “D987”in property owner account ID column 216. Row 222 indicates that aproperty owner identified as DEF456 has a vehicle lien identified asLIEN456 on a property identified by VIN12345678 with a lien holderidentified by FI987 that has a debt balance of $1,234.00 and that thedebt balance information is updated. Further, the property owneridentified as DEF456 has an account with member financial institutions120 identified by D987.

Rows 218 and 220 demonstrate that the same property owner can havemultiple liens on the same property with different lien holders. In anexample, lien holder FI987 may be one of the member financialinstitutions 120 and has kept the lien balance information updated,while lien holder F1654 may be one of the third party lien holders 130and has not kept the lien balance updated. Rows 218 and 22 demonstratethat that lien holders may hold multiple different types of liens withdifferent property owners (e.g., lien holder FI987 holds both mortgageand vehicle liens with multiple different property owners). Rows 218,220, and 222 further demonstrate how unique identifiers (e.g., realestate addresses and VINs) can be used to identify a plurality of liensassociate with a property. Further, rows 218, 220, and 222 demonstratethat maintaining updated balances on debt associated with liens, totaldebt associated with a property can be determined.

Modifications, additions, or omissions may be made to table 200. Table200 may include more, different, or less fields, and may include anyinformation relevant to communicating and maintaining property data.Table 200 may include any suitable amount of information and may bestored in any suitable type or number of memories.

FIG. 3 illustrates a flow diagram of an example method for communicatingproperty data, according to certain embodiments of the presentdisclosure.

Method 300 begins at step 302. At step 304 it is determined (e.g., bylien holder interface module 140) whether lien data has been received(e.g., from lien holders such as member financial institutions 120and/or third party lien holders 130). If lien data has not beenreceived, the method returns to step 304. If lien data has beenreceived, the method proceeds to step 306. At step 306, it is determined(e.g., by lien holder interface module 140) whether lien authenticationdata has been received (e.g., from lien holders such as member financialinstitutions 120 and/or third party lien holders 130). If lienauthentication data has not been received, the method returns to step306. If lien data has been received, the method proceeds to step 308. Atstep 308, the received lien data and lien authentication data are stored(e.g., in database 148 of lien holder interface module 140). At step310, it is determined (e.g., by lien holder interface module 140)whether the received lien data is valid. Validation processes arediscussed in more detail above with respect to FIG. 1. If the lien datais not validated, the method ends at step 316. If the lien data isvalidated, the method proceeds to step 312. At step 312, it isdetermined (e.g., by lien holder interface module 140) whether updatedlien data is required (e.g., from the lien holder). For example, if thecurrent balance of a debt associated with a lien has not been updatedwithin a payment period (e.g., as defined by a debt payment schedule),the current balance may be out of date. If no updated lien data isrequired, the method ends at step 316. If updated lien data is required,the method proceeds to step 314 and updated lien data is requested(e.g., by lien holder interface module 140) from the lien holder. Atstep 316 the method ends.

Modifications, additions, or omissions may be made to method 300. Themethod may include more, fewer, or other steps. Additionally, steps maybe performed in any suitable order, in parallel, and/or sequentially.Any suitable component of may perform one or more steps of method 300.

FIG. 4 illustrates a flow diagram of an example method for communicatingproperty data, according to certain embodiments of the presentdisclosure.

Method 400 begins at step 402. At step 404, it is determined (e.g., bylien holder interface module 140) whether lien data has been received(e.g., from lien holders such as member financial institutions 120and/or third party lien holders 130). If lien data has not beenreceived, the method returns to step 404. If lien data has beenreceived, the method continues to step 406 and the lien data is stored(e.g., in database 148 of lien holder interface module 140). At step408, it is determined (e.g., by lien holder interface module 140)whether a property payment request has been received (e.g., by aproperty insurer, property purchaser, or lender considering the propertyas collateral). If a property payment request has been received, themethod proceeds to step 410. At step 410, it is determined (e.g., bylien holder interface module 140) whether a subject property identifiedin the property payment request is stored in a database (e.g., database148 of lien holder interface module 140). If the subject property is notstored, the method ends at step 418. If the subject property is stored,the method proceeds to step 412. At step 412, one or more liens areidentified (e.g., by lien holder interface module 140) that areassociated with the subject property. At step 414, one or more lienholders are identified (e.g., by lien holder interface module 140) thatare associated with the identified liens associated with the subjectproperty. At step 416, the identified liens and lien holders arecommunicated (e.g., by lien holder interface module 140) to therequesting party. At step 418, method 400 ends.

Modifications, additions, or omissions may be made to method 400. Themethod may include more, fewer, or other steps. Additionally, steps maybe performed in any suitable order, in parallel, and/or sequentially.Any suitable component of may perform one or more steps of method 400.

Certain embodiments of the present disclosure may provide one or moretechnical advantages having specific technical effects.

In certain embodiments, a system is operable to provide a centralizedrepository associating property with liens, thereby conserving thecomputational resources and bandwidth consumed by searching disparateresources to identify liens on a property.

In particular embodiments, a system is operable to determine an amountof debt associated with one or more liens on a property, therebyconserving the computational resources and bandwidth consumed bysearching disparate resources to determine an amount of debt associatedwith a property.

In an embodiment, a system is operable to allocate a payment associatedwith a property between the property owner and lien holders, therebyconserving the computational resources and bandwidth consumed bysearching disparate resources to determine payment allocations for theproperty owner and lien holders.

Other technical advantages of the present disclosure will be readilyapparent to one skilled in the art from the following figures,descriptions, and claims. Moreover, while specific advantages have beenenumerated above, various embodiments may include all, some, or none ofthe enumerated advantages.

What is claimed is:
 1. A system for communicating property data,comprising: one or more interfaces operable to receive at a centralizedrepository: lien data from a first resource, wherein the first resourceis as least one of a commercial bank, a savings and loan association, acredit union, an Internet bank, a mutual fund company, a brokerage firm,or a credit card company; and lien authenticating data from a secondresource, wherein the second resource is independent from the firstresource and is at least one of a tax records database, a propertyrecords database, or a real estate database; one or more memoriescommunicatively coupled to the one or more interfaces, the one or morememories operable to store at the centralized repository the receivedlien data from the first resource and the received lien authenticationdata from the second resource; one or more processors communicativelycoupled to the one or more memories, the one or more processors operableto: determine, based on the received lien authentication data from thesecond resource, that the received lien data is valid; and determine,based on the received lien data from the first resource, that a receivedbalance of debt associated with the lien needs to be updated; whereinthe determination that the received balance of the debt associated withthe lien needs to be updated is based on at least: a repayment schedulefor the balance of the debt associated with the lien; or a receipt of aproperty payment request from the holder of the lien; and the one ormore interfaces further operable to: display an indication that thereceived balance of debt associated with the lien needs to be updated;communicate a request to the holder of the lien to submit updated lieninformation; receive updated lien data from the holder of the lien,wherein the updated lien data comprises a payment related to a property;and display the updated lien data; the one or more memories furtheroperable to store the updated lien data; and the one or more processorsfurther operable to: allocate a payment for the property between aproperty owner and the holder of the lien; and disburse the payment forthe property between the property owner and the holder of the lien.
 2. Asystem for communicating property data, comprising: one or moreinterfaces operable to receive at a centralized repository: lien datafrom a first resource, wherein the first resource is as least one of acommercial bank, a savings and loan association, a credit union, anInternet bank, a mutual fund company, a brokerage firm, or a credit cardcompany; and lien authentication data from a second resource, whereinthe second resource is independent from the first resource and is atleast one of a tax records database, a property records database, or areal estate database; one or more memories communicatively coupled tothe one or more interfaces, the one or more memories operable to storeat the centralized repository the received lien data from the firstresource and the received lien authentication data from the secondresource; and one or more processors communicatively coupled to the oneor more memories, the one or more processors operable to: determine,based on the received lien authentication data, that the received liendata is valid; determine, based on the received lien data, that areceived balance of debt associated with the lien needs to be updated;wherein the determination that the received balance of the debt isassociated with the lien needs to be updated is based on at least: therepayment schedule for the balance of the debt associated with the lien;or the receipt of a property payment request from the holder of thelien; allocate, based on the received lien data, a payment associatedwith the property between a property owner and the holder of the lien;and disburse the payment for the property between the property owner andholder of the lien.
 3. The system of claim 2, the one or more interfacesfurther operable to: communicate a request to the holder of the_lien tosubmit updated lien data; receive updated lien data from the holder ofthe lien; and display the updated lien data; and the one or moreprocessors further operable to store the updated lien data.
 4. Thesystem of claim 2, the one or more processors operable to validate thereceived lien data based on the received lien authentication data bycomparing the received lien authentication data to data received frompublic records.
 5. The system of claim 2, the one or more processorsfurther operable to determine a fee based on one or more of the receivedlien data and the received lien authentication data; and the one or moreinterfaces further operable to: communicate a fee request to the holderof the lien, the fee request indicating a fee charged to the lienholder; and receive a fee response from the holder of the lien, the feeresponse representing a commitment from the holder of the lien to paythe fee.
 6. The system of claim 2, the one or more processors furtheroperable to determine, based on the received lien data, that thereceived balance of debt associated with the lien needs to be updated bydetermining a payment date of the next scheduled payment on the balanceof debt and determining whether the balance of debt has been updatedwithin a threshold amount of time after that payment date.
 7. The systemof claim 2, the one or more processors further operable to determine,based on the received lien authentication data, that the received liendata is invalid; and the one or more interfaces further operable tocommunicate a notification to the lien holder indicating that the liendata is invalid.
 8. A non-transitory computer-readable medium comprisinglogic for communicating property data, the logic when executed by aprocessor operable to: receive lien data from a first resource, whereinthe first resource is as least one of a commercial bank, a savings andloan association, a credit union, an Internet bank, a mutual fundcompany, a brokerage firm, or a credit card company; receive lienauthentication data from a second resource, wherein the second resourceis independent from the first resource and is at least one of a taxrecords database, a property records database, or a real estatedatabase; store, at a centralized repository, the received lien datafrom the first resource and the received lien authentication data fromthe second resource; determine, based on the received lienauthentication data from the second resource, that the received liendata is valid; determine, based on the received lien data from the firstresource, that a received balance of debt associated with the lien needsto be updated; wherein the determination that the received balance ofthe debt associated with the lien needs to be updated is based on atleast: the repayment schedule for the balance of the debt associatedwith the lien; or the receipt of a property payment request from theholder of the lien; allocate, based on the received lien data, a paymentassociated with the property between a property owner and the holder ofthe lien; and disburse the payment associated with the property betweenthe property owner and the holder of the lien.
 9. The non-transitorycomputer-readable medium of claim 8, the logic further operable to:communicate a request to the holder of the lien to submit updated liendata; receive updated lien data from the holder of the lien; and storethe updated lien data.
 10. The non-transitory computer-readable mediumof claim 8, the logic further operable to validate the received liendata based on the received lien authentication data by comparing thereceived lien authentication data to data received from public records.11. The non-transitory computer-readable medium of claim 8, the logicfurther operable to: determine a fee based on one or more of thereceived lien data and the received lien authentication data;communicate a fee request to the holder of the lien, the fee requestindicating a fee charged to the lien holder; and receive a fee responsefrom the holder of the lien, the fee response representing a commitmentfrom the holder of the lien to pay the fee.
 12. The non-transitorycomputer-readable medium of claim 8, the logic further operable todetermine, based on the received lien data, that the received balance ofdebt associated with the lien needs to be updated by determining apayment date of the next scheduled payment on the balance of debt anddetermining whether the balance of debt has been updated within athreshold amount of time after that payment date.
 13. The non-transitorycomputer-readable medium of claim 8, the logic further operable to:determine, based on the received lien authentication data, that thereceived lien data is invalid; and communicate a notification to thelien holder indicating that the lien data is invalid.
 14. A method forcommunicating property data, comprising: receiving lien data from afirst resource, wherein the first resource is as least one of acommercial bank, a savings and loan association, a credit union, anInternet bank, a mutual fund company, a brokerage firm, or a credit cardcompany; and receiving lien authentication data from a second resource,wherein the second resource is at least one of a tax records database, aproperty records database, or a real estate database; storing, at acentralized repository, the received lien data from the first resourceand the received lien authentication data from the second resource;determining, by one or more processors, based on the received lienauthentication data from the second resource, that the received liendata is valid; determining, by one or more processors, based on thereceived lien data from the first resource, that a received balance ofdebt associated with the lien needs to be updated; wherein determiningthat the received balance of the debt associated with the lien needs tobe updated is based on at least: the repayment schedule for the balanceof the debt associated with the lien; or the receipt of a propertypayment request from the holder of the lien; allocating, by the one ormore processors, a payment associated with the property between aproperty owner and the holder of the lien; and dispersing, by the one ormore processors, the payment associated with the property between theproperty owner and the holder of the lien.
 15. The method of claim 14,further comprising: communicating a request to the holder of the lien tosubmit updated lien data; receiving updated lien data from the holder ofthe lien; and storing the updated lien data.
 16. The method of claim 14,further comprising validating, by one or more processors, the receivedlien data based on the received lien authentication data by comparingthe received lien authentication data to data received from publicrecords.
 17. The method of claim 14, further comprising: determining, byone or more processors, a fee based on one or more of the received liendata and the received lien authentication data; communicate a feerequest to the holder of the lien, the fee request indicating a feecharged to the lien holder; and receive a fee response from the holderof the lien, the fee response representing a commitment from the holderof the lien to pay the fee.
 18. The method of claim 14, furthercomprising determining, by one or more processors, based on the receivedlien data, that the received balance of debt associated with the lienneeds to be updated by determining a payment date of the next scheduledpayment on the balance of debt and determining whether the balance ofdebt has been updated within a threshold amount of time after thatpayment date.